The Juniper out-of-band management (OOBM) gateway router must be configured to have separate IGP instances for the managed network and management network.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-253992	JUEX-RT-000200	SV-253992r844009_rule		Medium

Description
If the gateway router is not a dedicated device for the OOBM network, implementation of several safeguards for containment of management and production traffic boundaries must occur. Since the managed and management network are separate routing domains, configuration of separate Interior Gateway Protocol routing instances is critical on the router to segregate traffic from each network.

STIG	Date
Juniper EX Series Switches Router Security Technical Implementation Guide	2023-03-23

Details

Check Text ( C-57444r844007_chk )
This requirement is not applicable for the DODIN Backbone. Verify that the OOBM interface is an adjacency in the Interior Gateway Protocol routing domain for the management network. Interfaces can only be assigned to one routing instance. [edit protocols ospf] interface .; << Cannot be assigned to a virtual routing instance. [edit routing-instances] { instance-type virtual-router; protocols { ospf { area { interface .; << Cannot be assigned to the default routing instance at [edit protocols]. } } } } Note: If the same interface is assigned to the default routing instance and to a virtual routing instance, commit fails. Some platforms support a routing-instance using the reserved name "mgmt_junos". On these platforms, configure the "mgmt_junos" instance and apply at the [edit system] hierarchy. [edit system] management-instance; [edit routing-instances] mgmt_junos { routing-options { static { route 0.0.0.0/0 next-hop ; } } } Note: Not all platforms support routing instances. If the router does not enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain, this is a finding.

Check Text ( C-57444r844007_chk )

This requirement is not applicable for the DODIN Backbone.

Verify that the OOBM interface is an adjacency in the Interior Gateway Protocol routing domain for the management network. Interfaces can only be assigned to one routing instance.

[edit protocols ospf]
interface .; << Cannot be assigned to a virtual routing instance.

[edit routing-instances]
{
instance-type virtual-router;
protocols {
ospf {
area {
interface .; << Cannot be assigned to the default routing instance at [edit protocols].
}
}
}
}

Note: If the same interface is assigned to the default routing instance and to a virtual routing instance, commit fails.

Some platforms support a routing-instance using the reserved name "mgmt_junos". On these platforms, configure the "mgmt_junos" instance and apply at the [edit system] hierarchy.
[edit system]
management-instance;

[edit routing-instances]
mgmt_junos {
routing-options {
static {
route 0.0.0.0/0 next-hop ;
}
}
}
Note: Not all platforms support routing instances.

If the router does not enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain, this is a finding.

Fix Text (F-57395r844008_fix)
This requirement is not applicable for the DODIN Backbone. Configure the router to enforce that Interior Gateway Protocol instances configured on the OOBM gateway router peer only with their own routing domain. set protocols ospf area interface . set routing-instances instance-type virtual-router set routing-instances protocols ospf area interface .